Skip to content

Conversation

@prathmesh-stripe
Copy link
Contributor

@prathmesh-stripe prathmesh-stripe commented Apr 15, 2025

Why?

In order to keep supporting new versions of Java we need to test against them.

What?

Added Java versions 21, 22, 23, 24 to our CI workflow.

See Also

@prathmesh-stripe prathmesh-stripe requested a review from a team as a code owner April 15, 2025 14:49
@prathmesh-stripe prathmesh-stripe requested review from xavdid-stripe and removed request for a team April 15, 2025 14:49
@prathmesh-stripe prathmesh-stripe enabled auto-merge (squash) April 15, 2025 15:03
Copy link
Member

@xavdid-stripe xavdid-stripe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it makes sense to add these because they're all current. But we probably don't need them long term. Basically all of our users are on LTS java versions (8, 11, 17, and 21).

Given that, in this PR, I'd also:

  • drop any older non-LTS versions we're currently testing
  • add a link to the java version support list so future readers know why we're testing
  • add a comment to codify which versions we should include in this list and why

@prathmesh-stripe prathmesh-stripe enabled auto-merge (squash) May 12, 2025 18:13
@prathmesh-stripe prathmesh-stripe merged commit d177cbc into master Jun 3, 2025
13 checks passed
@prathmesh-stripe prathmesh-stripe deleted the prathmesh/include-new-lang-versions-in-ci branch June 3, 2025 13:41
EncriptionFJ

This comment was marked as spam.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants